Specifying the Behaviour of Uml Collaborations Using Object-z
نویسندگان
چکیده
UML is a standard modelling language that is able to specify a wide range of object-oriented concepts. Among them, we have collaborations, that serve to realise use cases, a powerful abstraction concept. The behaviour part of a collaboration is rendered using collaboration diagrams. However, the lack of formalisation compromises the precision of the specification. By using formal description techniques, such as Object-Z, we can reason about the requirements and identify ambiguities and inconsistencies earlier in the development process. In general, we can say that formalisation helps obtaining a more reliable system. Our aim is to formalise collaborations Object-Z class schemas. This is accomplished by proposing an integrated formal process.
منابع مشابه
Synthesizing State-Machine Behaviour from UML Collaborations and Use Case Maps
Telecommunication services are provided as the joint effort of components, which collaborate in order to achieve the goal(s) of the service. UML 2.0 collaborations can be used to model services. Furthermore, they allow services to be described modularly and incrementally, since collaborations can be composed of subordinate collaborations. For such an approach to work, it is necessary to capture...
متن کاملToward a Formal Model of Software Components
We are interested in specifying component models in a way that allows us to analyze the interplay of components in general, and to concisely specify individual components. As a starting point for coming up with a technique of specifying component models, we consider JavaBeans. We capture the JavaBean component model using UML class diagrams, Object-Z, and life sequence charts.
متن کاملMapping Business Processes to Software Design Artifacts
This paper explains the structure of a project repository, which enables you to trace business processes and business rules to the architecture and design of the software system. The structure identifies types and instances of business processes, which are mapped to software design artifacts by means of refinements, realizations and collaborations at different levels of abstraction. Even when u...
متن کاملAvailability evaluation of Software architecture of object oriented Style using coloured Petri nets
Software architecture is one of the most fundamental products in the process of software development in the areas of behavioral or non- behavioral features like availability or transformability change. There are different ways to evaluate software architecture one of which is the creation of application model. An executable model of software architecture is an official description of architectu...
متن کاملFrom Contracts to Aspects in UML Designs
Separation of concerns is a basic engineering principle that is often applied in object-oriented analysis and design by dissociating functional aspects (business objects) from non-functional ones, such as persistency, fault-tolerance and so on. The Unified Modeling Language (UML) then gives the designer a rich, but somehow disorganized, set of views on her model as well as many features, such a...
متن کامل